Release 10.1A: OpenEdge Development:
Internationalizing Applications

OpenEdge support for multi-byte code pages

Table 8–6 lists the multi-byte code pages OpenEdge supports.

Table 8–6: Multi-byte code pages OpenEdge supports

Code page	Language
BIG-5	Traditional Chinese
CP949	Korean
CP950	Traditional Chinese
CP950-HKSCS	Traditional Chinese with Hong Kong supplementary character set
CP1361 Note: This is not convertible to UTF-8 and not recommended for use.	Korean
EUCJIS	Japanese
GB2312	Simplified Chinese
GB18030	Extended Chinese (that is, an extension of GB2312 that includes all characters defined in Unicode)
KSC5601	Korean
SHIFT-JIS	Japanese
UTF-8	Multi-lingual
UTF-16, UTF-16BE, UTF-16LE, UTF-32, UTF-32BE, UTF-32LE	Multi-lingual; for input and output, not for cpinternal

Note: The Thai language is also supported, by code page 620-2533. This is a single-byte code page for which some of the codepoints are combining characters. A single column could consist of up to three 620-2533 codepoints; however, it is not a multi-byte code page consisting of lead-byte and trail-byte combinations.

Additional GB18030 code page considerations

When working with the GB18030 code page, consider the following:

The GB18030 code page is a multi-byte code page, consisting of one-, two-, and four-byte characters, that extends the GB2312 code page and includes all characters defined in Unicode. Unlike most multi-byte code pages that OpenEdge supports, you cannot use the lead byte of multi-byte characters in the GB18030 code page to determine the character's length. Progress uses the International Components for Unicode (ICU) library to convert characters between the GB18030 code page and Unicode within the OpenEdge GUI client.
Progress supports the GB18030 code page, primarily, for file input and output. More specifically, you can use the GB18030 code page:
In settings for the -cpstream, -cplog, and -cpprint startup parameters.
With any 4GL CONVERT SOURCE/TARGET phrase that applies to files. For example:

INPUT FROM gb.txt CONVERT SOURCE "GB18030". COPY-LOB FROM FILE “gb.txt” TO myunicodeclob    CONVERT SOURCE CODEPAGE "GB18030".

With the ASC, CHR, and CODEPAGE-CONVERT functions (but if used as the target code page of CHR or CODEPAGE-CONVERT, you cannot use the resulting character or character string in the 4GL).
With file input and output in the SQL products.

You cannot use the GB18030 code page:

In other 4GL statements (not listed above).
As a CLOB or LONGCHAR code page.
In settings for the -cpinternal, -cpterm, -cprcodein, or -cprcodeout startup parameters.
As a database code page.
With the PROUTIL <db> -C CONVCHAR CONVERT command (although it can be used for CONVCHAR ANALYZE).